Embraer EMB-500 Phenom 100

Nicholas Services LLC

Nicholas Air flight JTZ356, an Embraer EMB-500 Phenom 100, N356N, sustained substantial damage when it collided with a box truck while taxing to the ramp on taxiway C after landing on runway 23R at Raleigh-Durham International Airport (RDU/KRDU), Raleigh, North Carolina. There were no reported injuries.

Prime Aviation Participações e Serviços S.A.

The aircraft took off from Viracopos Airport (SBKP), Campinas, SP, bound for São Paulo Catarina Executive Airport (SBJH), São Roque, SP, for a ferry flight, with two crew members on board. During landing, the aircraft overran the right-hand side of the runway, coming to a stop against the fence that delimited the airfield.

Tracbel Group

While approaching São Pedro Airport by night, the aircraft crashed in a wooded area short of the airfield, bursting into flames. All four occupants evacuated the cabin and the aircraft was totally destroyed by a post crash fire.

Sage Aviation

The airplane crashed while on approach to runway 14 at Montgomery County Airpark (GAI), Gaithersburg, Maryland. The airplane impacted three houses and the ground about 3/4 mile from the approach end of the runway. A postcrash fire involving the airplane and one of the three houses, which contained three occupants, ensued. The pilot, the two passengers, and the three people in the house died as a result of the accident. The airplane was destroyed by impact forces and postcrash fire. The flight was operating on an instrument flight rules flight plan under the provisions of 14 Code of Federal Regulations (CFR) Part 91. Visual meteorological conditions prevailed at the time of the accident. Data from the airplane’s cockpit voice and data recorder (CVDR) indicated that the takeoff about 0945 from Horace Williams Airport, Chapel Hill, North Carolina, and the cruise portion of the flight were uneventful. CVDR data showed that about 15 minutes after takeoff, the passenger in the right cockpit seat made a statement that the airplane was “in the clouds.” A few seconds later, the airplane’s engine anti-ice system and the wing and horizontal stabilizer deice system were manually activated for about 2 minutes before they were manually turned off. About 6 minutes later, a recording from the automated weather observing system (AWOS) at GAI began transmitting over the pilot’s audio channel, containing sufficient information to indicate that conditions were conducive to icing during the approach to GAI. The CVDR recorded no activity or faults during the rest of the flight for either ice protection system, indicating that the pilot did not turn the systems back on. Before the airplane descended through 10,000 ft, in keeping with procedures in the EMB-500 Pilot Operating Handbook, the pilot was expected to perform the Descent checklist items in the Quick Reference Handbook (QRH), which the pilot should have had available in the airplane during the flight. Based on the AWOS-reported weather conditions, the pilot should have performed the Descent checklist items that appeared in the Normal Icing Conditions checklist, which included turning on the engine anti-ice and wing and horizontal stabilizer deice systems. That action, in turn, would require the pilot to use landing distance performance data that take into account the deice system’s activation. CVDR data show that, before beginning the descent, the pilot set the landing reference (Vref) speed at 92 knots, indicating that he used performance data for operation with the wing and horizontal stabilizer deice system turned off and an airplane landing weight less than the airplane’s actual weight. Using the appropriate Normal Icing Conditions checklist and accurate airplane weight, the pilot should have flown the approach at 126 knots (a Vref of 121 knots +5 knots) to account for the icing conditions.

JetSuite

The pilots of the very light jet were conducting a positioning flight in instrument meteorological conditions. The flight was cleared by air traffic control for the instrument landing system (ILS) approach; upon being cleared for landing, the tower controller reported to the crew that there was no standing water on the runway. Review of the airplane's flight data recorder (FDR) data revealed that the airplane reached 50 ft above touchdown zone elevation (TDZE) at an indicated airspeed of 118 knots (KIAS). The airplane crossed the runway displaced threshold about 112 KIAS, and it touched down on the runway at 104 KIAS with about a 7-knot tailwind. FDR data revealed that, about 1.6 seconds after touchdown of the main landing gear, the nose landing gear touched down and the pilot's brake pedal input increased, with intermediate oscillations, over a period of 7.5 seconds before reaching full pedal deflection. During this time, the airplane achieved its maximum wheel braking friction coefficient and deceleration. The cockpit voice recorder recorded both pilots express concern the that the airplane was not slowing. About 4 seconds after the airplane reached maximum deceleration, the pilot applied the emergency parking brake (EPB). Upon application of the EPB, the wheel speed dropped to zero and the airplane began to skid, which resulted in reverted-rubber hydroplaning, further decreasing the airplane's stopping performance. The airplane continued past the end of the runway, crossed a service road, and came to rest in a drainage ditch. Postaccident examination of the brake system and data downloaded from the brake control unit indicated that it functioned as commanded during the landing. The airplane was not equipped with thrust reversers or spoilers to aid in deceleration. The operator's standard operating procedures required pilots to conduct a go-around if the airspeed at 50 ft above TDZE exceeded 111 kts. Further, the landing distances published in the airplane flight manual (AFM) are based on the airplane slowing to its reference speed (Vref) of 101 KIAS at 50 ft over the runway threshold. The airplane's speed at that time exceeded Vref, which resulted in an increased runway distance required to stop; however, landing distance calculations performed in accordance with the AFM showed that the airplane should still have been able to stop on the available runway. An airplane performance study also showed that the airplane had adequate distance available on which to stop had the pilot continued to apply maximum braking rather than engage the EPB. The application of the EPB resulted in skidding, which increased the stopping distance. Although the runway was not contaminated with standing water at the time of the accident, the performance study revealed that the maximum wheel braking friction coefficient was significantly less than the values derived from the unfactored wet runway landing distances published in the AFM, and was more consistent with the AFM-provided landing distances for runways contaminated with standing water. Federal Aviation Administration Safety Alert for Operators (SAFO) 15009 warns operators that, "the advisory data for wet runway landings may not provide a safe stopping margin under all conditions" and advised them to assume "a braking action of medium or fair when computing time-of-arrival landing performance or [increase] the factor applied to the wet runway time-of-arrival landing performance data." It is likely that, based on the landing data in the AFM, the crew expected a faster rate of deceleration upon application of maximum braking; when that rate of deceleration was not achieved, the pilot chose to engage the EPB, which only further degraded the airplane's braking performance.

JetSuite

Following an uneventful flight, the flight crew briefed the arrival to the destination airport and set the calculated landing speeds. The captain and the first officer reported that during final approach, it felt like the airplane was “pushed up” as the wind shifted to a tailwind or updraft before landing near the runway number markings. Upon touchdown, the captain applied the brakes and thought that the initial braking was effective; however, he noticed the airplane was not slowing down. The captain applied maximum braking, and the airplane began to veer to the right; he was able to correct back to the runway centerline, but the airplane subsequently exited the departure end of the runway and traveled down a steep embankment. A pilot-rated passenger reported that throughout the approach to landing, he thought the airplane was high and thought that the excessive altitude continued through and into the base-to-final turn. He added that the bank angle of this turn seemed greater than 45 degrees. Recorded communication from the cockpit voice and data recorder (CVDR) revealed that during the approach to landing, the flight crew performed the landing checks, and the captain noted difficulty judging the approach. About 1 minute later, the recording revealed that the ground warning proximity system reported “five hundred” followed by a “sink rate, pull up” alert about 16 seconds later. Data from the CVDR revealed that about 23 seconds before weight-on-wheels was recorded, the airplane was at an indicated airspeed of about 124 knots and descending. The data showed that this approximate airspeed was maintained until about 3 seconds before weight-on-wheels. The recorded data further showed that the approach speed was set to 120 knots, and the landing reference speed (vREF) was set to 97 knots. Using the reported airplane configuration and the 3.5-knot headwind that was reported at the time of the approach and landing, calculations indicate that the vREF speed should have been about 101 knots indicated airspeed, which would have required a landing distance of about 3,112 feet. Utilizing the same airplane configuration and wind condition with the flight’s reported 124 knot indicated airspeed just before touchdown, the landing distance was calculated to be about 5,624 feet. The intended runway for landing was 5,132-feet long with a 1.9 percent downward slope gradient, and a 123-foot long overrun area. A postaccident examination of the airplane, including the braking system, revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The pilot misjudged the airplane’s speed during the final approach, which resulted in runway overrun.

SAVE Comercial e Importadora

Following an uneventful flight from Campo de Marte, the crew initiated the approach to runway 10 which is 961 metres long. After touchdown, the crew started the braking procedure but the aircraft skidded on runway and cartwheeled. It overran, lost its both main gears and came to rest six metres further. Both pilots escaped uninjured and the aircraft was damaged beyond repair.